Vehicle information delivery and management system and method

ABSTRACT

A technique and method for vehicle information delivery and management includes: receiving, by a management module of a service provider manager associated with a service provider, a notification from an application executing on a client device of an end user that vehicle data corresponding to a vehicle being viewed by the end user on a premises of the service provider has been displayed to the end user; storing, by the management module, the vehicle data corresponding to the viewed vehicle; and storing, by the management module, a time that the vehicle was viewed by the end user.

BACKGROUND

A vehicle information disclosure sheet, which can also commonly bereferred to as a Monroney sticker, is typically affixed to a side windowof a vehicle. Generally, a vehicle information disclosure sheet includesinformation such as the make, model and year of the vehicle, the vehicleidentification number (VIN), the estimated fuel efficiency of thevehicle, a list of standard and optional features included in thevehicle, the manufacturer suggested retail price (MSRP) of the vehicleand other information pertaining to the vehicle. An addendum may alsoaccompany and/or be affixed to the window of the vehicle near oradjacent the Monroney sticker that includes additional,locally-installed optional features available on the vehicle (e.g.,dealer/seller add-ons, such as window tinting, wheel locks, upholsteryprotection, etc.) including their respective prices.

When a potential buyer views the vehicle information disclosure sheetand wishes to obtain additional information about a specific vehicle,the potential buyer usually will need to speak to a salesrepresentative. However, this can be time consuming, especially if asales representative is not readily available. Also, a potential buyermay be reluctant to speak to a sales representative for fear ofreceiving an aggressive sales pitch. In addition, when the dealer lot isclosed, no sales representatives will be present to speak with thepotential buyer.

BRIEF SUMMARY

According to one aspect of the present disclosure a method and techniquefor vehicle information delivery and management is disclosed. The methodincludes: receiving, by a management module of a service providermanager associated with a service provider, a notification from anapplication executing on a client device of an end user that vehicledata corresponding to a vehicle being viewed by the end user on apremises of the service provider has been displayed to the end user;storing, by the management module, the vehicle data corresponding to theviewed vehicle; and storing, by the management module, a time that thevehicle was viewed by the end user.

According to another aspect of the present disclosure, a computerprogram product for vehicle information delivery and service isdisclosed. The computer program product comprises a computer readablestorage medium having program instructions embodied therewith, theprogram instructions executable by a processor of a client device tocause the processor to perform a method comprising: scanning for awireless signal emitted by an identification (ID) object associated witha vehicle; responsive to detecting the wireless signal, determiningvehicle data corresponding to the vehicle; displaying the vehicle datato the end user; and transmitting an indication that the vehicle isbeing viewed by an end user of the client device to a service providersystem.

According to yet another aspect of the present disclosure, a system forvehicle information delivery and service is disclosed. The systemincludes a service provider manager comprising a processor unit and aservice management module, the service management module executable bythe processor unit to: receive a notification from an applicationexecuting on a client device of an end user that vehicle datacorresponding to a vehicle being viewed by the end user has beendisplayed to the end user; and notify at least one employee of a serviceprovider of the notification.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

For a more complete understanding of the present application, theobjects and advantages thereof, reference is now made to the followingdescriptions taken in conjunction with the accompanying drawings, inwhich:

FIG. 1 is an embodiment of a network of data processing systems in whichthe illustrative embodiments of the present disclosure may beimplemented;

FIG. 2 is an embodiment of a data processing system in which theillustrative embodiments of the present disclosure may be implemented;

FIG. 3 is a diagram illustrating an embodiment of a distributedcomputing environment in which illustrative embodiments of a system forvehicle information delivery and management according to the presentdisclosure may be implemented;

FIG. 4 is a diagram illustrating an embodiment of a client device of asystem for vehicle information delivery and management according to thepresent disclosure;

FIG. 5 is a diagram illustrating an embodiment of a graphical userinterface displayable on the client device of FIG. 4 in a system forvehicle information delivery and management according to the presentdisclosure;

FIG. 6 is a diagram illustrating another embodiment of a graphical userinterface displayable on the client device of FIG. 4 in a system forvehicle information delivery and management according to the presentdisclosure;

FIG. 7 is a diagram illustrating an embodiment of a service providersystem for vehicle information delivery and management according to thepresent disclosure;

FIG. 8 is a flow diagram illustrating an embodiment of a method forvehicle information delivery and management according to the presentdisclosure; and

FIG. 9 is a flow diagram illustrating another embodiment of a method forvehicle information delivery and management according to the presentdisclosure.

DETAILED DESCRIPTION

Embodiments of the present disclosure provide a method, system andcomputer program product for vehicle information delivery andmanagement. Embodiments of the present disclosure enable the efficientmanagement of vehicle information delivery and service. For example,embodiments of the present disclosure enable an end user, using anapplication residing and executing on a portable electronic device, toretrieve and store electronic versions of Monroney and/or other vehicleinformation corresponding to a desired or “viewed” vehicle, including ina desired language, thereby enabling the Monroney sticker to be removedand/or omitted from the vehicle (which may decrease the likelihood ofvehicular accidents during test drives due to impaired visibility fromthe Monroney sticker). The end user, utilizing the application, maystore a variety of types of information for various vehicles (e.g., fromone or more vehicle service providers/dealerships) for laterevaluation/retrieval. Further, modules/applications residing on and/ormade available to various personnel at the service provider/dealershipenables such personnel to more efficiently respond to and provideservice to the end user/customer. For example, in some embodiments,personnel most closely matching various criteria for responding to anend user/customer request can be identified and selected. Further, dataacquired corresponding to which vehicles have been viewed (during and/orafter normal business hours) by end users/customers may better enablethe dealership to gauge consumer interest in particular vehicles. Thus,for example, in some embodiments, the method and technique includes:receiving, by a management module of a service provider managerassociated with a service provider, a notification from an applicationexecuting on a client device of an end user that vehicle datacorresponding to a vehicle being viewed by the end user on a premises ofthe service provider has been displayed to the end user; storing, by themanagement module, the vehicle data corresponding to the viewed vehicle;and storing, by the management module, a time that the vehicle wasviewed by the end user.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, and a floppy disk, and any suitable combination of theforegoing. A computer readable storage medium, as used herein, is not tobe construed as being transitory signals per se, such as radio waves orother freely propagating electromagnetic waves, electromagnetic wavespropagating through a waveguide or other transmission media (e.g., lightpulses passing through a fiber-optic cable), or electrical signalstransmitted through a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages. The computer readableprogram instructions may execute entirely on the user's computer, partlyon the user's computer, as a stand-alone software package, partly on theuser's computer and partly on a remote computer or entirely on theremote computer or server. In the latter scenario, the remote computermay be connected to the user's computer through any type of network,including a local area network (LAN) or a wide area network (WAN), orthe connection may be made to an external computer (for example, throughthe Internet using an Internet Service Provider). In some embodiments,electronic circuitry including, for example, programmable logiccircuitry, field-programmable gate arrays (FPGA), or programmable logicarrays (PLA) may execute the computer readable program instructions byutilizing state information of the computer readable programinstructions to personalize the electronic circuitry, in order toperform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

With reference now to the Figures and in particular with reference toFIGS. 1-2, exemplary diagrams of data processing environments areprovided in which illustrative embodiments of the present disclosure maybe implemented. It should be appreciated that FIGS. 1-2 are onlyexemplary and are not intended to assert or imply any limitation withregard to the environments in which different embodiments may beimplemented. Many modifications to the depicted environments may bemade.

FIG. 1 is a pictorial representation of a network of data processingsystems in which illustrative embodiments of the present disclosure maybe implemented. Network data processing system 100 is a network ofcomputers in which the illustrative embodiments of the presentdisclosure may be implemented. Network data processing system 100contains network 130, which is the medium used to provide communicationslinks between various devices and computers connected together withinnetwork data processing system 100. Network 130 may include connections,such as wire, wireless communication links, or fiber optic cables.

In some embodiments, server 140 and server 150 connect to network 130along with data store 160. In addition, clients 110 and 120 connect tonetwork 130. Clients 110 and 120 may be, for example, personal computersor network computers. In the depicted example, server 140 provides dataand/or services such as, but not limited to, data files, operatingsystem images, and applications to clients 110 and 120. Network dataprocessing system 100 may include additional servers, clients, and otherdevices.

In the depicted example, network data processing system 100 is theInternet with network 130 representing a worldwide collection ofnetworks and gateways that use the Transmission ControlProtocol/Internet Protocol (TCP/IP) suite of protocols to communicatewith one another. At the heart of the Internet is a backbone ofhigh-speed data communication lines between major nodes or hostcomputers, consisting of thousands of commercial, governmental,educational and other computer systems that route data and messages. Ofcourse, network data processing system 100 also may be implemented as anumber of different types of networks, such as for example, an intranet,a local area network (LAN), or a wide area network (WAN). FIG. 1 isintended as an example, and not as an architectural limitation for thedifferent illustrative embodiments.

FIG. 2 is an embodiment of a data processing system 200 such as, but notlimited to, client 110 and/or server 140 in which an embodiment of asystem for vehicle information delivery and management according to thepresent disclosure may be implemented. In this embodiment, dataprocessing system 200 includes a bus or communications fabric 202, whichprovides communications between processor unit 204, memory 206,persistent storage 208, communications unit 210, input/output (I/O) unit212, and display 214.

Processor unit 204 serves to execute instructions for software that maybe loaded into memory 206. Processor unit 204 may be a set of one ormore processors or may be a multi-processor core, depending on theparticular implementation. Further, processor unit 204 may beimplemented using one or more heterogeneous processor systems in which amain processor is present with secondary processors on a single chip. Asanother illustrative example, processor unit 204 may be a symmetricmulti-processor system containing multiple processors of the same type.

In some embodiments, memory 206 may be a random access memory or anyother suitable volatile or non-volatile storage device. Persistentstorage 208 may take various forms depending on the particularimplementation. For example, persistent storage 208 may contain one ormore components or devices. Persistent storage 208 may be a hard drive,a flash memory, a rewritable optical disk, a rewritable magnetic tape,or some combination of the above. The media used by persistent storage208 also may be removable such as, but not limited to, a removable harddrive.

Communications unit 210 provides for communications with other dataprocessing systems or devices. In these examples, communications unit210 is a network interface card. Modems, cable modem and Ethernet cardsare just a few of the currently available types of network interfaceadapters. Communications unit 210 may provide communications through theuse of either or both physical and wireless communications links.

Input/output unit 212 enables input and output of data with otherdevices that may be connected to data processing system 200. In someembodiments, input/output unit 212 may provide a connection for userinput through a keyboard and mouse. Further, input/output unit 212 maysend output to a printer. Display 214 provides a mechanism to displayinformation to a user.

Instructions for the operating system and applications or programs arelocated on persistent storage 208. These instructions may be loaded intomemory 206 for execution by processor unit 204. The processes of thedifferent embodiments may be performed by processor unit 204 usingcomputer implemented instructions, which may be located in a memory,such as memory 206. These instructions are referred to as program code,computer usable program code, or computer readable program code that maybe read and executed by a processor in processor unit 204. The programcode in the different embodiments may be embodied on different physicalor tangible computer readable media, such as memory 206 or persistentstorage 208.

Program code 216 is located in a functional form on computer readablemedia 218 that is selectively removable and may be loaded onto ortransferred to data processing system 200 for execution by processorunit 204. Program code 216 and computer readable media 218 form computerprogram product 220 in these examples. In one example, computer readablemedia 218 may be in a tangible form, such as, for example, an optical ormagnetic disc that is inserted or placed into a drive or other devicethat is part of persistent storage 208 for transfer onto a storagedevice, such as a hard drive that is part of persistent storage 208. Ina tangible form, computer readable media 218 also may take the form of apersistent storage, such as a hard drive, a thumb drive, or a flashmemory that is connected to data processing system 200. The tangibleform of computer readable media 218 is also referred to as computerrecordable storage media. In some instances, computer readable media 218may not be removable.

Alternatively, program code 216 may be transferred to data processingsystem 200 from computer readable media 218 through a communicationslink to communications unit 210 and/or through a connection toinput/output unit 212. The communications link and/or the connection maybe physical or wireless in the illustrative examples.

The different components illustrated for data processing system 200 arenot meant to provide architectural limitations to the manner in whichdifferent embodiments may be implemented. The different illustrativeembodiments may be implemented in a data processing system includingcomponents in addition to or in place of those illustrated for dataprocessing system 200. Other components shown in FIG. 2 can be variedfrom the illustrative examples shown. For example, a storage device indata processing system 200 is any hardware apparatus that may storedata. Memory 206, persistent storage 208, and computer readable media218 are examples of storage devices in a tangible form.

FIG. 3 is an illustrative embodiment of a system 300 for vehicleinformation delivery and management. Various components of system 300may be implemented on data processing systems or platforms such as, butnot limited to, servers 140 and/or 150, clients 110 and/or 120, or atother data processing system locations. In FIG. 3, system 300 includes anumber of vehicles 310 (e.g., vehicles 310 ₁-310_(n)). Vehicles 310 maycomprise any type of vehicle such as, but not limited to, automobiles,trucks, vans, motorcycles, boats, campers, recreation vehicles, etc. Itshould be understood that embodiments of the present invention may alsobe applied to other types of devices/goods/items instead of or inaddition to vehicles (e.g., homes/apartments/condos for sale/lease,consumer electronic equipment, or other types of items where additionalinformation about the item, or an alternate mechanism for providinginformation about the item, may be desired). In the illustratedembodiment, system 300 also includes a service provider system 320, athird party system 330, a client device 340, and a network 350communicatively couplable to service provider system 320, third partysystem 330, and/or client device 340. Network 350 may comprise theInternet, an intranet, a local area network (LAN), a wide area network(WAN), or any type of wired/wireless network (e.g., a wirelesstelephone/data network). Service provider system 320 and third partysystem 330 may comprise any type of local and/or remote data processingsystem (e.g., locally and/or remotely located (e.g., cloud-basedsystems) computing platforms, such as server 140/150 and/or clients110/120).

In the illustrated embodiment, service provider system 320 may comprisea data processing system of a vehicle seller (e.g., an automobiledealership), and third party system 330 may comprise a data processingsystem of a vehicle manufacturer, vehicle safety resource, etc. However,it should be understood that systems 320 and/or 330 may comprisecomputing platforms associated with other entities. Client device 340may comprise any type of portable computing device such as, but notlimited to, a telephone/smartphone, laptop computer, a tablet computer,a personal digital assistant, or other types of portable data processingsystem capable of presenting/displaying information to an end userthereof.

In FIG. 3, each vehicle 310 includes an identification (ID) object 360(e.g., 360 ₁-360 _(n)) associated therewith. In some embodiments, IDobject 360 comprises a beacon object for emitting/transmitting awireless signal for transmitting data associated with a respectivevehicle 360 to client device 340 (e.g., using radio-frequencyidentification (RFID) signals/tags, Bluetooth low-energy (BLE) wirelesstechnology (e.g., an IBEACON) or other type of wirelesssignal/technology). ID object 360 may be located within/inside vehicle310, on the vehicle 310, or may be otherwise associated with arespective vehicle 310. ID object 360 may be programmed (e.g., bydealership personnel or other individuals) to contain and/or configuredto store thereon information corresponding to an associated/linkedvehicle 310 (e.g., Monroney information, dealer addendum information,etc.). In some embodiments, ID object 360 may comprise a barcode (e.g.,a universal product code (UPC) barcode, a matrix or two-dimensionalbarcode (e.g., a quick response (QR) code), etc.) or other type ofmachine-readable indicia that, when read, may comprise informationassociated with a respective linked vehicle 310 and/or may direct clientdevice 340 to information associated with a respective vehicle 310(e.g., a link to a dealership website).

As will be described in greater detail below, client device 340 maycomprise hardware, software and/or a combination of the foregoing, thatmay scan/detect/receive a signal from ID object 360 when in closeproximity thereto (or read an ID object 360 (e.g., a barcode) in someembodiments) and automatically display data associated with a respectivevehicle 310. For example, in some embodiments, ID object 360 may beprogrammed to contain and transfer to client device 340 informationtypically present on a Monroney sticker and/or dealer addendum, therebydisplaying to the end user of client device 340 an electronic version ofthe Monroney sticker/addendum.

FIG. 4 is a diagram illustrating an embodiment of client device 340according to the present invention. In FIG. 4, client device 340includes a processor unit 410, a display 412 (e.g., a liquid crystaldisplay (LCD) or other type of device for displaying information), amemory 414, a graphical user interface (GUI) 416 and a transceiver 418.Transceiver 418 may comprise any type or device/module for receivingand/or transmitting wireless signals/communications. In the illustratedembodiment, memory 414 includes an ID application 420, vehicle data 422,service provider data 424, and profile data 426. GUI 416 may comprise aninterface displayable on display 412 for enabling an end user of clientdevice 340 to view/select various functions/features available via IDapplication 420.

ID application 420 is configured to scan/detect/read/receive a signalfrom ID object 360 (FIG. 3) and perform various functions in responsethereto. For example, in some embodiments, ID application 420 isconfigured to receive a signal from ID object 360, obtain informationassociated with a respective vehicle 310 associated with the ID object360, and display the information to an end user via display 412. In someembodiments, ID application 420 may be configured to read/decode IDobject 360 in the form of a barcode and display the decoded informationto an end user via display 412. ID application 420 may be implemented inany suitable manner using known techniques that may be hardware-based,software-based, or some combination of both. For example, ID application420 may comprise software, logic and/or executable code for performingvarious functions as described herein (e.g., residing as software and/oran algorithm running on a processor unit, hardware logic residing in aprocessor or other type of logic chip, centralized in a singleintegrated circuit or distributed among different chips in a dataprocessing system).

In FIG. 4, vehicle data 422 includes Monroney data 430, addendum data432, showroom data 434 and end user vehicle data 436. Monroney data 430may comprise information typically included on a Monroney stickeraffixed to a particular vehicle 310. Addendum data 432 may compriseinformation associated with additional, locally-installed optionalfeatures on the respective vehicle 310 (e.g., dealer/seller add-ons,such as window tinting, wheel locks, upholstery protection, etc.)including their respective prices. Showroom data 434 may compriseinformation associated with one or more vehicles 310 stored by an enduser for later retrieval. For example, in some embodiments, the end usermay visit multiple dealerships (or view multiple, different vehicles 310at a single dealership) and store in the end user's “showroom” Monroneydata 430 and addendum data 432 for each desired vehicle. Thus, if theend user would like to later reevaluate a particular vehicle, the enduser may select a GUI 416 option to view vehicles stored in the enduser's “showroom.” In some embodiments, ID application 420 may beconfigured to compare the different vehicles (or vehicle information) asstored as showroom data 434 to evaluate differences between the“showroom” vehicles. Additionally, in some embodiments, ID application420 may be configured to provide a translated version of Monroney data430 and addendum data 432. For example, in some embodiments, GUI 416 maybe configured with various language options such that, in response to aselection of a particular language option (e.g., Spanish), Monroney data430 and addendum data 432 are translated and displayed by ID application420 in the selected/desired language. In some embodiments, ID object 360may also and/or alternatively be configured/programmed to includeMonroney data 430 and addendum data 432 in different languages.

End user vehicle data 436 may comprise information associated with oneor more vehicles owned by an end user (e.g., owned by an end user ofclient device 340 that may be potential trade-in vehicles on a purchaseof a new vehicle 310 (i.e., new to the end user)). For example, the enduser may use ID application 420 to enter and store information regardingvehicles currently owned by the end user (e.g., make, model, year,color, options, mileage, etc.). In some embodiments, the end user mayenter a VIN number, and ID application 420 may be configured toautomatically connect to and/or communicate with a third party site(e.g., third party system 330 (FIG. 3)) to gather information about thevehicle based on the VIN number.

Service provider data 424 may comprise information associated with aprovider of vehicles 310 (e.g., a seller/dealership). Service providerdata 424 may comprise general information about the dealership (e.g.,business hours, contact phone number/emails, etc.), a logo of thedealership, and, as will be described in greater detail below,information associated with contacting dealership representatives inresponse to a selection of various GUI 416 options by the end user. Insome embodiments, ID application 420 is configured to obtain serviceprovider data 424 on a real time, or near real time basis, based on aproximity of client device 340 to a particular dealership. For example,in some embodiments, in response to an end user of client device 340launching ID application 420, ID application 420 may automaticallyconnect to and/or otherwise communicate with a data processing system(e.g., via transceiver 418) of a dealership in close (or closest)proximity thereto and update service provider data 424 based on thereceived information. Thus, in some embodiments, service provider data424 may be automatically updated and displayed based on proximity to arespective/participating dealership. Profile data 426 may compriseinformation related to the end user of client device 340 (e.g., name,address, contact information, etc.).

FIG. 5 is a diagram illustrating an embodiment of a display of GUI 416according to the present disclosure. In FIG. 5, GUI 416 includes variousselectable/clickable icons/buttons such as a “view vehicle” 510 icon, a“my showroom” 512 icon, a “my garage” 514 icon, and a “dealership” 516icon. View vehicle 510 icon, in response to being selected, may enablethe user to view information associated with one or more vehicles 310detected/identified by ID application 420. For example, in someembodiments, ID application 420 may detect and/or receive signals fromone or more ID objects 360 associated with respective vehicles 310located in close proximity to client device 340. If only a singlevehicle 310 is detected/identified, ID application 420 may automaticallydisplay vehicle data 422 (e.g., Monroney data 430 and addendum data 432)for the detected vehicle 310. If multiple vehicles 310 are detected, IDapplication 420 may display an image and/or brief summary of eachdetected/identified vehicle 310 and prompt the user for a selection of aparticular vehicle 310. For example, for vehicles 310 located in closeproximity to each other, ID application 420 may detect and/or receivesignals from multiple respective ID objects 360. In response to aselection of a particular vehicle 310, ID application 420 displaysvehicle data 422 (e.g., Monroney data 430 and addendum data 432) for theselected vehicle 310. The view vehicle 510 icon may also causeadditional icons/options to be displayed/selected by the user, such asan icon that would connect the end user to a manufacturer website toobtain additional information about the vehicle, a link to third partyvehicle safety information (e.g., the IIHS), a screen depicting currentincentives/rebates available on the vehicle, a payment calculator,etc.).

ID application 420 may also be configured to display additional searchoptions for selection and/or input by an end user of client device 340.For example, in some embodiments, a GUI 416 screen/display page mayinclude an input option for the end user to input a VIN number, stocknumber, scan a barcode, or other feature that may be used to locatedand/or identify a particular vehicle 310. As an example, an end user mayview a dealership website while at home and identify a vehicle that theend user would like to see in person at the dealership. The end user mayenter/store a VIN number, stock number, or other identifying informationin ID application 420 that the end user obtained from the dealershipwebsite. Upon visiting the dealership or being on the dealershippremises, the end user may select the view vehicle 510 icon as well asselect an option and/or information corresponding to the previouslystored VIN number/stock number. ID application 420 may be configured tonotify the end user (e.g., via a display signal, audio signal, etc.) inresponse to detecting a signal from a corresponding ID object 360 thatmatches the stored search criteria (e.g., matching the VIN number/stocknumber stored by the end user). Thus, in this example, the end user maywalk along a row of vehicles 310 and be notified when a vehicle 310matching the searched for vehicle criteria has been detected/located.Thus, it should be understood that ID application 420 may be configuredwith various/different search options to enable the end user to locateand identify a particular vehicle 310. As indicated above, the viewvehicle 510 icon may also comprise a GUI 416 screen/display that enablesthe end user to input/scan a barcode (e.g., affixed and/or located on/ina particular vehicle 310) to automatically display Monroney data 430 andaddendum data 432 for the selected vehicle 310. ID application 420 mayalso store the applicable Monroney data 430 and addendum data 432 forthe viewed vehicle 310 as showroom data 434 in response to the end userselecting an “add to my showroom” icon.

ID application 420 may also be configured to display showroom data 434in response to a selection by the end user of the my showroom 512 icon.For example, in response a selection of the my showroom 512 icon,Monroney data 430 and addendum data 432 for vehicles 310 previouslyviewed and stored as showroom data 434 may be displayed by IDapplication 420. ID application 420 may also be configured to provideand display a side-by-side comparison of vehicles 310 selected from theshowroom data 434.

ID application 420 may also be configured to display end user vehicledata 436 in response to a selection by the end user of the my garage 514icon. For example, in some embodiments, ID application 420 may, inresponse to a selection of the my garage 514 icon, display vehicleinformation of end user-owned vehicles previously stored as end uservehicle data 436 and/or enable the end user to enter/store vehicleinformation to be stored as end user vehicle data 436. In someembodiments, ID application 420 may be configured to scan and/or receiveinput of a VIN number and automatically access a third party system(e.g., system 330) to obtain and automatically populate various fieldsof information (e.g., make, model, year, etc.) and enable the end userto enter other types of information (e.g., mileage). ID application 420may then store the entered information as end user vehicle data 436. Enduser vehicle data 436 may also include image files and/or other types ofinformation that may be displayed to enable a dealership to evaluate anend user-owned vehicle for a potential trade-in value even if the enduser-owned vehicle is not presently onsite at the dealership. In someembodiments, vehicle information of a vehicle stored as showroom data434 may be automatically stored as end user vehicle data 436 as a resultof the end user purchasing such vehicle. For example, in someembodiments, information associated with one of the vehicles 310previously stored as showroom data 434 (e.g., that the end user isconsidering purchasing) may be automatically transferred to end uservehicle data 436 in response to a selection of an input icon in the “myshowroom” screen (e.g., a selection icon displaying “purchased”).Correspondingly, if a vehicle identified and stored as end user vehicledata 436 is used as a trade-in on a new vehicle purchase, ID application420 may automatically purge/delete the vehicle information from end uservehicle data 436 (e.g., in response to a selection by the end user of a“traded in” icon on an end user-owned vehicle screen of GUI 416). Aswill be described in greater detail below, the addition or deletion ofvehicle information in showroom data 434 and/or end user vehicle data436 as described above may be accomplished without end user action(e.g., action performed by the dealership may be automaticallycommunicated to ID application 420 to, for example, move a “showroom”vehicle to the “my garage” of the end user in response to a purchase,and delete a vehicle from the “my garage” of the end user in response toa trade-in of the vehicle).

ID application 420 may also be configured to display one or moreselectable options to the end user to communicate with the dealership inresponse to a selection by the end user of the dealership 516 icon. Forexample, FIG. 6 is a diagram illustrating an embodiment of a display ofGUI 416 in response to selection of the dealership 516 icon of FIG. 5according to the present disclosure. In FIG. 6, GUI 416 includes variousselectable/clickable icons/buttons such as an “inquire to dealership”610 icon, a “contact a salesperson” 612 icon, a “request a manager” 614icon, and a “dealership ratings & review” 616 icon, and a “salespersonratings & review” 618 icon. The dealership ratings & review 616 icon andthe salesperson ratings & review 618 icon may automatically link IDapplication 420 to a third party or dealership site providing ratingsand reviews of the respective dealership and salesperson. The inquire todealership 610 icon, when selected, may cause ID application 420 tocommunicate with service provider system 320 (e.g., the dealership) toenable the end user to contact/send an inquiry to the dealership. Forexample, ID application 420 may enable the end user to send an email,text, phone call, leave a voice message, open a chat dialog, or otheraction with the particular dealership. The contact a salesperson 612icon and request a manager 614 icon, when selected, causes IDapplication 420 to communicate with system 320 to contact a respectivesalesperson or manager of the dealership. This contact request may be inthe form of a telephone contact, text, email, chat dialog, or may causea signal/alert/notice to be given to a respective salesperson/managerthat an end user (customer) onsite at the dealership would like anin-person visit with the respective salesperson/manager. As indicatedabove in connection with other options, ID application 420 may alsoenable a selection of language, gender, ethnicity, or othercharacteristic to be selected/identified by the end user such that asalesperson/manager matching (or closest to matching) the desiredcriteria may be notified of the desired contact request.

Referring to FIG. 4, ID application 420 also includes a notificationmodule 440 and a test module 450. Notification module 440 may be used toprovide various types of information gathered/stored by ID application420 to system 320 and/or system 330, automatically and/or in response toend user input. For example, notification module 440 may be used toinitiate communications with system 320 in response to request tocontact a salesperson/manager. Notification module 440 may also beconfigured to automatically communicate to system 320 the variousvehicles 310 selected/viewed by an end user/customer. For example, insome embodiments, in response to ID application 420 detecting a signalfrom a respective ID object 360 and displaying vehicle data 422 based onthe ID object 360 detected, notification module 440 may automaticallycommunicate the corresponding information about the respective vehicle310 (along with other information) to system 320. The informationcommunicated to system 320 may include the identity (or identifier) ofthe vehicle, the date/time the action occurred, information about theend user/customer (e.g., profile data 426), etc. In some embodiments,notification module 440 communicates the information in real time (ornear real time) to enable the dealership to better service a potentialcustomer (e.g., by alerting the dealership of what vehicle is beingevaluated, the date/time of evaluation, the location of the vehicle onthe premises, etc.). It should be understood that the types ofinformation transmitted by ID application 420 to service provider system320 and/or third party system 330 may vary, and the actions and/orfunctions that invoke the transmission may vary.

Test module 450 may be configured to simulate a test drive (e.g.,provide a virtual test drive) of a selected vehicle. For example, insome embodiments, as part of the GUI 416 screen in a “view vehicle”screen, the end user may select a “virtual test drive” icon. In responseto the selection of the virtual test drive icon, test module 450 mayprovide an interactive multimedia environment for the end user to learnadditional information about the vehicle (e.g., experience a series ofinteractive views/media presentations of the vehicle and enable the enduser to visually and/or audibly experience various aspect of thevehicle). For example, test module 450 may be used to download and/orstream various multimedia files to represent a test drive of thevehicle. The multimedia files may simulate a test drive by providing aview to the end user looking out through the front window (as if drivingthe vehicle), provide sounds of the engine, in-cabin chimes/alerts, thedisplay and use of in-cabin controls, changes in speed, etc., to providethe end user with a sensory experience simulating a test drive of thevehicle. Test module 450 may also be configured to receive user inputselections on various displayed screens of the test drive images toenable various information and/or option selections to be engaged (e.g.,responses to push button controls, changes in engine sound in response adesired increase in acceleration, audio output of a navigation system,etc.).

FIG. 7 is a diagram illustrating an embodiment of service providersystem 320 according to the present disclosure. System 320 may beimplemented on data processing systems or platforms such as, but notlimited to, servers 140 and/or 150, clients 110 and/or 120, or at otherdata processing system locations. In an example embodiment, system 320may be implemented by a vehicle dealership and connected to network 350.In the illustrated embodiment, system 320 comprises a service providermanager 710 and a service provider client 720. Service provider manager710 may comprise hardware, software and/or a combination of theforegoing to provide management functionality for a vehicle dealership(e.g., employed by management personnel at the dealership). Serviceprovider client 720 may comprise hardware, software and/or a combinationof the foregoing to provide non-management functionality for a vehicledealership (e.g., employed by a salesperson at the dealership) or usedby managers to access/utilize management information available frommanager 710. However, it should be understood that various management ornon-management roles and/or functionality may be shared between managersand non-managers at the dealership or made available to managers andnon-managers differently as described herein.

In the illustrated embodiment, service provider manager 710 comprises aprocessor unit 730 and a memory 732. Memory 732 includes provider data734, a key module 736 and a service management module 738. Provider data734 may comprise various information associated with a service provider(e.g., a vehicle dealership) such as, but not limited to, registrationdata 740, location data 742, vehicle ID data 744, customer data 746,vehicle view data 748, key data 750, and test data 752. As will bedescribed in greater detail below, key module 736 may be used to monitorthe availability of, to reserve, to dispense, etc., a key (orignition-enabling device) for the operation of a vehicle (e.g., toenable a test drive). Service management module 738 is configured toacquire various types of information associated with vehicles 310, endusers/customers, employees of the dealership, etc. Service managementmodule 738 may also be used to respond to requests for contact by acustomer (e.g., via the “contact a salesperson” 612 icon and/or “requesta manager” 614 icon of ID application 420), selection/notification ofcertain employees in response to a request for contact by a customer,monitoring/tracking the locations of employees on the dealershippremises available to assist a customer, and/or other functions asdescribed herein. Key module 736 and/or management module 738 may beimplemented in any suitable manner using known techniques that may behardware-based, software-based, or some combination of both. Forexample, key module 736 and/or management module 738 may comprisesoftware, logic and/or executable code for performing various functionsas described herein (e.g., residing as software and/or an algorithmrunning on a processor unit, hardware logic residing in a processor orother type of logic chip, centralized in a single integrated circuit ordistributed among different chips in a data processing system).

Registration data 740 may comprise information associated with variousmanagers/salespersons/employees currently onsite at the dealershipand/or ready/available to assist customers. For example, as will bedescribed in greater detail below, a manager/salesperson/employeeutilizing client 720 may register with service management module 738 toenable the location of the manager/salesperson/employee to be identifiedon the premises of the dealership and/or otherwise enable themanager/salesperson/employee to be contacted/designated in response to acustomer requesting assistance (e.g., via the “contact a salesperson”612 icon and/or “request a manager” 614 icon of ID application 420).Registration data 740 may also include information associated withvarious characteristics of the registered employee (e.g., languagesspoken, familiarity with certain vehicle types, gender, etc.).Registration data 740 may also indicate the availability status of anemployee of the dealership to assist a customer (e.g., on-premises butunavailable (e.g., currently with a customer)).

Location data 742 may comprise information associated with the locationof various vehicles 310 on the dealership premises and/or location ofmanagers/salespersons/employees on the dealership premises. For example,using global positioning system (GPS) data or other types of positiontracking mechanisms related to various client devices 720 used by themanagers/salespersons/employees (e.g., smartphone devices, tablets,etc.), the locations of the managers/salespersons/employees may beidentified on the dealership premises to enable certain employees to beidentified/selected to assist a customer. Location data 742 may alsoinclude information associated with the locations of vehicles 310 (e.g.,correlated to respective ID objects 360) on the dealership premises. Insome embodiments, location data 742 may be used by service managementmodule 738 to display a map of the dealership premises indicating thelocations of vehicles 310 (including highlighting or otherwise notifyingdealership personnel of specific vehicles 310 that are currently being“viewed” using ID application 420, the locations of end users/customerson the dealership premises requesting contact/assistance, and/or thelocations of dealership personnel on the dealership premises.

Vehicle ID data 744 may comprise information associated with the variousvehicles 310 available from the service provider/dealership. Forexample, vehicle ID data 744 may comprise Monroney information (e.g.,such as Monroney data 430), addendum information (e.g., such as addendumdata 432), or other types of information corresponding to vehicles 310.Customer data 746 may comprise information associated with variouscustomers (e.g., end users utilizing ID application 420) that may beon-premises at the dealership and/or that were on-premises at thedealership. For example, in some embodiments, in response to launchingof ID application 420 by an end user of client device 340, notificationmodule 440 may automatically (or after receipt by an acceptance promptfrom an end user of client device 340) transmit profile data 426 tomanager 710 and store profile data 426 as customer data 746.Notification module 440 may also automatically (or after receipt by anacceptance prompt from an end user of client device 340) transmitshowroom data 434 and/or end user vehicle data 436 to manager 710 andstore showroom data 434 and/or end user vehicle data 436 as customerdata 746. Thus, customer data 746 would enable the dealership to readilyidentify vehicles the customer is considering purchasing and/orpotential vehicles as trade-ins.

Vehicle view data 748 may comprise information related to which vehicles310 have been viewed/evaluated by end users/customers utilizing IDapplication 420. For example, as described above, ID application 420 maybe configured to transmit in real time (or near real time) to manager710 vehicles 310 viewed/evaluated by end users/customers to enableservice management module 738 (or a dealership employee viewing vehicleview data 748) to analyze trends (e.g., based on the analysis ofhistorical vehicle view data 748), identify customers at variouslocations of the dealership premises (e.g., based on the vehicle 310being viewed), identify certain salespersons in close proximity to theend user/customer, etc. Stored vehicle view data 748 may also beanalyzed from a historical perspective (e.g., as opposed to real timeanalysis) to determine the most common vehicles viewed, to determine thelocations on the dealership premises where customers are looking, todetermine/identify patterns in vehicles being considered (e.g., colors,option packages, etc.).

Key data 750 may comprise information associated with a keymanagement/dispensing system or machine utilized by the dealership. Forexample, in some embodiments, the dispensing/receipt (checking out andchecking in) of a key/ignition device for vehicles 310 iscontrolled/managed electronically and/or by computer-relatedimplementation/machine by a dealership so that use of the keys byemployees of the dealership can be monitored and/or controlled. Key data750 may comprise information associated with the availability of akey/ignition device (e.g., whether the key has been checked out, when itwas checked out, who checked it out, whether the key has been reserved,etc.).

Test data 752 may comprise information associated with a virtual testdrive of a vehicle 310. For example, in some embodiments, test data 752may comprise multimedia files that may be downloaded/transferred to testmodule 450 to enable a virtual test drive of a vehicle 310. However, itshould be understood that multimedia content for a virtual test drivemay be otherwise stored/located.

Service management module 738 may also be used to provide communicationsdirectly between dealership personnel. For example, in some embodiments,service management module 738 may interface with clients 720 to providegeneral announcements (e.g., via text message, email, or otherwise),communicate with particular employees (e.g., request that a particularemployee go to a service desk to meet a waiting end user/customer), etc.

In the illustrated embodiment, client 720 comprises a processor unit 760and a memory 762. Memory 762 includes a service module 770, customerdata 772 and key data 774. Service module 770 is configured to interfacewith service management module 738 and/or key module 736 toprovide/receive various types of information associated with vehicles310, end users/customers, employees of the dealership, key/ignitiondevices, etc. For example, service module 770 may be used to notify adealership employee of a request for contact by a customer (e.g., viathe “contact a salesperson” 612 icon and/or “request a manager” 614 iconof ID application 420), to register the employee and/or client device720 with service management module 738 (e.g., providing registrationdata 740 for location monitoring, to register an availability status ofthe employee, etc.), to reserve/check-out/check-in a key/ignition devicefor a vehicle, to acquire vehicle 310 information in response to acustomer inquiry, etc. Service module 770 may be implemented in anysuitable manner using known techniques that may be hardware-based,software-based, or some combination of both. For example, service module770 may comprise software, logic and/or executable code for performingvarious functions as described herein (e.g., residing as software and/oran algorithm running on a processor unit, hardware logic residing in aprocessor or other type of logic chip, centralized in a singleintegrated circuit or distributed among different chips in a dataprocessing system).

Customer data 772 may comprise information associated with endusers/customers utilizing ID application 420 (e.g., profile data 426,showroom data 434 and/or end user vehicle data 436). Customer data 772may also include information associated with a location of a particularcustomer on the dealership premises (e.g., based on a current vehicle310 being viewed). Key data 774 may comprise information associated withthe availability and/or reservation/checking-out/checking-in of akey/ignition device. For example, if a particular customer would like totest drive a vehicle, an employee/salesperson may utilize service module770 to interface with key module 736 to determine the availability of akey, to reserve a key, to check-out a key and/or to check-in a key. Insome embodiments, key module 736 may be configured withproximity-detecting hardware/software (or use location data 742) todetect when a requesting salesperson (or a salesperson that has reserveda key) is in close proximity to a key dispensing location of the keymachine/system to automatically dispense the key to the salesperson.

Thus, in operation, an end user/customer may launch ID application 420on the end user's/customer's client device 340. ID application 420 willscan, listen for and/or detect signals from ID objects 360 in proximityto the end user. In response to detecting a signal from one or more IDobjects 360, ID application 420 will display information associated witha respective vehicle 310 linked to the respective ID object 360. If morethan one vehicle 310 is identified/detected (or even if only a singlevehicle 310 is detected), ID application 420 may display a brief summaryof the identified vehicle(s) 310 to enable the end user to select adesired vehicle 310 to view. Upon a selection of a desired vehicle 310,ID application 420 displays vehicle data 422 corresponding to theselected/identified vehicle 310 (e.g., Monroney data 430 and, ifincluded, addendum data 432). ID application 420 (e.g., via one or moreGUI 416 screens) enables the user to obtain/view additional informationassociated with the selected vehicle 310 (e.g., sales incentives, linksto third party sites, etc.). Based on profile data 426 and/or otherinputs received by ID application 420 from the end user/customer, theinformation on the selected vehicle 310 may be provided/displayed in adesired language.

In some embodiments, ID application 420 (e.g., via notification module440) may transmit profile data 426, showroom data 434 and/or end uservehicle data 436 to service provider manager 710. Profile data 426,showroom data 434 and/or end user vehicle data 436 may be stored onmanager 710 by service management module 738. Notification module 440may also transmit any updates to profile data 426, showroom data 434and/or end user vehicle data 436 as received (e.g., a real time (or nearreal time) update in response to an end user adding a new “viewed”vehicle 310 to the end user's “showroom”). ID application 420 may alsobe configured to automatically forward to manager 710 informationassociated with any “viewed” vehicle 310. Thus, in some embodiments,even outside normal business hours of the dealership, manager 710 (e.g.,via service management module 738) is collecting information associatedwith “viewed” vehicles 310 (e.g., stored as vehicle view data 748).Service management module 738 may be configured to notify amanager/salesperson/employee of the dealership in real time (or nearreal time) of updates/changes to vehicle view data 748, and/or vehicleview data 748 may be made available for review and/or analysis duringother times. Vehicle view data 748 may be analyzed, transformed, orotherwise manipulated by service management module 738 to identifytrends, patterns, or other desired characteristics associated with thedealership and/or vehicles 310.

In response to detecting a “view” of a vehicle 310 by ID application420, service management module 738 may alert a dealership manager,salesperson or other employee (e.g., a text, audio alert, etc., on asmartphone, tablet or other device). Service management module 738 mayinterface with service module 770 of a corresponding client device 720of the employee to provide such notification. Service management module738 may alert a particular manager, salesperson or other employeeaccording to a desired selection/matching algorithm, according to around-robin technique, or other method.

In response to an input from the end user via ID application 420 forcontact by a salesperson or manager of the dealership, servicemanagement module 738 receives such notification from ID application420. Service management module 738 may acquire/identify vehicle ID data744 associated with the “viewed” vehicle 310, determine/identify alocation of the vehicle 310/customer on the dealership premises, andautomatically identify a particular salesperson/manager to assist thecustomer. For example, in some embodiments, service management module738 may analyze registration data 740 to identify availablesalespersons/managers, determine which salespersons/managers have alanguage preference indicated by the end user/customer, identifysalespersons/managers most familiar with the vehicle 310 of interest,locate/identify salespersons/managers in close proximity to the enduser/customer, or apply another algorithm to identify and select aparticular salesperson/manager to respond to the request. Servicemanagement module 738 may then notify the selected salesperson/manager(e.g., via a telephone call, text, or other type of alert). Whennotifying a particular salesperson/manager of the contact request,service management module 738 may also forward various information tothe client 720 of the selected salesperson/manager (e.g., customer data746, vehicle ID data 744 of the vehicle 310 being viewed, location data742, etc.). In some embodiments, service management module 738 may beconfigured to automatically send a message to a respective IDapplication 420 in response to a “view” of a vehicle to inquire if theend user/customer would like some assistance (e.g., immediately, orafter some predetermined amount of time).

Service management module 738 may also be used to establish acommunication link between an end user/customer and amanager/salesperson. For example, an end user/customer may desirecontact with a manager/salesperson via a chat dialog. Service managementmodule 738 may initiate and manage the chat session between the customerand salesperson/manager over network 350. Service management module 738may also manage and control other types of communications between theend user/customer and dealership personnel.

As described above, ID application 420 may also be used to search for aparticular vehicle 310 and/or be used to scan a barcode or other type ofindicator to obtain information about a selected/desired vehicle 310. Insome embodiments, regardless of the mechanism used by an enduser/customer to “view” a particular vehicle 310, ID application 420 maynotify and transmit related information to service management module 738(e.g., vehicle data 422 associated with the “viewed” vehicle 310,profile data 426, showroom data 434 and/or end user vehicle data 436).

In some embodiments, service management module 738 may also be usedinvoke a change to vehicle information stored as showroom data 434and/or end user vehicle data 436 on an end user client device 340. Forexample, as a result of the end user purchasing a vehicle included inshowroom data 434 (e.g., the “my showroom” page(s) displayable by IDapplication 420), service management module 738 may cause ID application420 to transfer such vehicle information to the “my garage” page(s)displayable by the ID application 420 (e.g., now included in end uservehicle data 436). Correspondingly, if a vehicle identified and storedas end user vehicle data 436 is used as a trade-in on a new vehiclepurchase, service management module 738 may cause ID application 420 topurge/delete the vehicle information from end user vehicle data 436.

FIG. 8 is a flow diagram illustrating an embodiment of a method forvehicle management. The method begins at block 802, where ID application420 is launched and scans/detects/reads one or more ID objects 360. Atblock 804, ID application determines vehicle data 422 corresponding tothe scanned/detected/read ID objects 360. At decision block 806, adetermination is made by ID application 420 whether multiple ID objects360 have been scanned/detected/read. If so, the method proceeds to block808, where ID application 420 generates and displays a summary of eachvehicle 310 corresponding to each scanned/detected/read ID object 360.In some embodiments, ID application 420 may prompt the end user toselect a particular vehicle 310 from the summary display. At block 810,ID application 420 receives a selection of a particular vehicle 310 fromthe summary display. At block 812, ID application 420 displays vehicledata 422 (e.g., Monroney data 430 and, if present, addendum data 432).At block 806, if a determination is made by ID application 420 that asingle ID object 360 has been scanned/detected/read, the method mayproceed from decisional block 806 to block 812. However, as describedabove, even if a single ID object 360 has been scanned/detected/read, IDapplication 420 may initially provide a brief summary of thecorresponding vehicle 310.

At block 814, ID application 420 transmits information regarding the“viewed” vehicle 310 to service provider manager 710. At block 816, IDapplication 420 transmits end user profile data 426 to service providermanager 710. For example, ID application 420 may be configured toreceive and store various types of information about the enduser/customer. At block 818, ID application 420 transmits showroom data434 to service provider manager 710. Showroom data 434 may includesaved/stored information of other vehicles being considered by the enduser/customer (whether viewed/considered at the current dealership or adifferent dealership). At block 820, ID application 420 transmits enduser vehicle data 436 to service provider manager 710. For example, IDapplication 420 may be configured to receive and store as end uservehicle data 436 information regarding vehicles currently owned by theend user/customer. End user vehicle data 436 may be used by dealershippersonnel to evaluate potential trade-in vehicles on a purchase of a newvehicle.

At decisional block 822, a determination is made whether the end userhas added the current “viewed” vehicle 310 to the end user's “myshowroom.” If so, the method proceeds to block 824, where ID application420 stores vehicle data 422 corresponding to the “viewed” vehicle 310 tothe “my showroom” of the end user (e.g., adding/updating showroom data434) and transmits the added/updated showroom data 434 to serviceprovider manager 710. If at decisional block 822 the “viewed” vehicle310 was not added to the “my showroom” of the end user, the methodproceeds to block 826. At block 826, ID application 420 communicates anyreceived request from the end user for contact/assistance (e.g., arequest for contact from a salesperson, manager, etc.) to serviceprovider manager 710.

FIG. 9 is a flow diagram illustrating another embodiment of a method forvehicle management. The method begins at block 902, where servicemanagement module 738 receives, stores and/or updates registration data740 corresponding to dealership employees/clients 720. For example, asdescribed above, employees of the dealership may register their client720 devices and/or otherwise provide status information of theirpresence/availability to assist end users/customers. At block 904,service management module 738 receives and stores location datacorresponding to vehicles 310 corresponding to respective ID objects360. For example, service management module 738 may store locationinformation corresponding to the vehicle 310 locations to enable suchlocation information to be displayed on a dealership premises map orotherwise.

At block 906, service management module 738 monitors the location and/oravailability of personnel of the dealership. For example, personnel mayutilize service module 770 on respective clients 720 to update theiravailability status, which is thereby communicated to service managementmodule 738. Service management module 738 may also use GPS data and/orother location monitoring techniques to monitor the locations ofdealership personnel on the dealership premises. At block 908, servicemanagement module 738 receives, stores and/or otherwise updates key data750 for vehicles 310. For example, personnel may utilize service module770 on respective clients 720 to interface with key module 736 todetermine the availability of a key/ignition device for a particularvehicle 310, check-in/check-out a key, and/or reserve a key.

At block 910, service management module 738 receives a notification(e.g., from ID application 420 of a particular end user's client device340) of a “viewed” vehicle by such end user. At block 912, servicemanagement module 738 receives and stores vehicle ID data 744 and/orlocation data 742 corresponding to the “viewed” vehicle. At block 914,service management module 738 receives profile data 426 from IDapplication 420 corresponding to the “viewing” end user. At block 916,service management module 738 receives showroom data 434 (if available)from ID application 420 corresponding to the “viewing” end user. Atblock 918, service management module 738 receives end user vehicle data436 (if available) from ID application 420 corresponding to the“viewing” end user. At block 920, service management module 738 notifiesdesired personnel of the dealership (e.g., manager, salesperson, etc.)that a vehicle 310 has been “viewed.”

At decisional block 922, a determination is made whether a contact orassistance request has been received from the end user via a respectiveID application 420. If so, the method proceeds to block 924, whereservice management module 738 may identify/select a particularmanager/salesperson/employee to respond to the request. For example, insome embodiments, service management module 738 may receive (e.g., aspart of profile data 426 or otherwise) an indication of a languagepreference or other desired characteristic. Service management module738 may search registration data 740 to locate available employees ofthe dealership having the desired language capability. Servicemanagement module 738 may also determine and/or otherwise identifycertain available employees most knowledgeable about the “viewed”vehicle of interest, closest in proximity to the vehicle 310/end user,or other selection criteria. Thus, in some embodiments, servicemanagement module 738 may be configured to execute a search/matchingalgorithm to identify/select a desired and/or best employee candidatefor responding to the end user request.

At block 926, service management module 738 forwards to the selecteddealership employee (e.g., communicating and/or interfacing with servicemodule of client 720 of the employee) location data 742, vehicle ID data744, showroom data 434 and/or end user vehicle data 436 to enable theselected employee to best respond to the end user request. If atdecisional block 922 a determination is made that no contact request hasyet been received from an end user/customer, the method proceeds toblock 928. At block 928, service management module 738 continuesmonitoring for indications of “viewed” vehicles 310 by endusers/customers.

Thus, embodiments of the present invention enables the efficientmanagement of vehicle information delivery and service. For example, asindicated above, system 300 enables an end user to retrieve and storeelectronic versions of Monroney and/or other vehicle informationcorresponding to a desired or “viewed” vehicle, including in a desiredlanguage, thereby enabling the Monroney sticker to be removed and/oromitted from the vehicle (which may decrease the likelihood of vehicularaccidents during test drives due to impaired visibility from theMonroney sticker). The end user, utilizing ID application 420, may storea variety of types of information for various vehicles (e.g., from oneor more vehicle service providers/dealerships) for laterevaluation/retrieval. Further, modules/applications residing on and/ormade available to various personnel at the service provider/dealershipenables such personnel to more efficiently respond to and provideservice to the end user/customer. For example, in some embodiments,personnel most closely matching various criteria for responding to anend user/customer request can be identified and selected. Further, dataacquired corresponding to which vehicles 310 have been viewed (duringand/or after normal business hours) may better enable the dealership togauge consumer interest in particular vehicles.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the disclosure.As used herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the present disclosure has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the disclosure in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the disclosure. Theembodiment was chosen and described in order to best explain theprinciples of the disclosure and the practical application, and toenable others of ordinary skill in the art to understand the disclosurefor various embodiments with various modifications as are suited to theparticular use contemplated.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

What is claimed is:
 1. A system, comprising: a service provider managercomprising a processor unit and a service management module, the servicemanagement module executable by the processor unit to: receive anotification from an application executing on a client device of an enduser that vehicle data corresponding to a vehicle being viewed by theend user has been displayed to the end user; receive registration datacorresponding to personnel of a service provider, the registration datacomprising availability status information of the respective personnel;monitor a location of the respective personnel on a premises of theservice provider; and notify at least one of the personnel of theservice provider of the notification; and a key module executable by theprocessor unit to cause an ignition-enabling device for operation of thevehicle viewed by the end user to be dispensed from a key managementmachine of the service provider.
 2. The system of claim 1, wherein theservice management module is configured to: receive a request forassistance from the end user; and analyze the registration data toidentify and select the at least one of the personnel to respond to therequest.
 3. The system of claim 2, wherein the service management moduleis configured to forward to the selected at least one of the personnelthe vehicle data corresponding to the vehicle being viewed by the enduser.
 4. The system of claim 1, wherein the service management module isconfigured to: receive a request for assistance from the end user; andanalyze the location of the personnel to identify and select the atleast one of the personnel in close proximity to the end user to respondto the request.
 5. The system of claim 1, wherein the service managementmodule is configured to: receive profile data from the applicationcorresponding to the end user; and receive showroom data from theapplication, the showroom data indicating one or more vehiclespreviously viewed by the end user.
 6. The system of claim 1, wherein theservice management module is configured to: receive a request forassistance from the end user; select at least one of the personnel torespond to the request; and notify the selected at least one of thepersonnel to respond to the request.
 7. A method, comprising: receiving,by a management module of a service provider manager associated with aservice provider, a notification from an application executing on aclient device of an end user that vehicle data corresponding to avehicle being viewed by the end user on a premises of the serviceprovider has been displayed to the end user; storing, by the managementmodule, the vehicle data corresponding to the viewed vehicle; storing,by the management module, a time that the vehicle was viewed by the enduser; notifying, by the management module, at least one employee of theservice provider of the notification; receiving, by the managementmodule, profile data corresponding to the end user; forwarding, by themanagement module, the profile data to the at least one employee; andcausing, by the service provider manager, an ignition-enabling devicefor operation of the vehicle viewed by the user to be dispensed from akey management machine of the service provider.
 8. The method of claim7, further comprising: receiving, by the management module, registrationdata corresponding to personnel of the service provider, theregistration data comprising availability status information of therespective personnel; and monitoring, by the management module, alocation of the respective personnel on the premises of the serviceprovider.
 9. The method of claim 7, further comprising: receiving, bythe management module, registration data corresponding to personnel ofthe service provider, the registration data comprising availabilitystatus information of the respective personnel; receiving, by themanagement module, a request for assistance from the end user;selecting, by the management module, at least one of the personnel torespond to the request; and notifying, by the management module, theselected one of the personnel to respond to the request.
 10. The methodof claim 9, further comprising forwarding, by the management module, thevehicle data corresponding to the vehicle being viewed by the end user.